Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1938

Introduce new context for web-resourse

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Low Engagement
    • None
    • API and Integrations
    • None
    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Service Desk plugin has a number of screens but those screens does not have a context. As a result, other plugins cannot attach anything to those views like the portal page (servicedesk/customer/portal/XYZ).
      So, it will be useful to introduce a new web resource context for a portal page.

      If your plugin adds a number of screens to the application, you may find it useful to introduce a new web resource context for your plugin that your plugin web resources (or any other plugin web resource) can hook into, to be automatically included on these screens.
      To introduce a new context in your plugin Velocity templates, you can call the requireResourcesForContext() method on the WebResourceManager object from your Velocity templates:

      $webResourceManager.requireResourcesForContext("com.acme.plugin.fancy-context")

      This will include any resource in the page that specifies a context like this in its definition: <context>com.acme.plugin.fancy-context</context>.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              78e7e652d6fe Andriy Hospodarysko
              Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync